Enhanced Wake-Up Signal Based Power Saving for a Wireless Device

ABSTRACT

A technique for power saving, comprising establishing a radio resource control (RRC) connection with a wireless system, entering an RRC connected mode based on the established RRC connection, receiving, from the wireless system, configuration information indicating a discontinuous reception (DRX) cycle time, a DRX on time period, and an offset time, determining an enhanced wake-up signal (EWUS) monitoring occasion for a DRX cycle based on the offset time and the DRX on time period, monitoring, during a first DRX cycle, for an EWUS during the EWUS monitoring occasion associated with the first DRX cycle, receiving, from the wireless system, the EWUS during the EWUS monitoring occasion, determining that the EWUS indicates that the wireless device skip one or more future EWUS monitoring occasions, and skipping monitoring for the EWUS based on the indicated skipped one or more future EWUS monitoring occasions.

FIELD

The present application relates to wireless devices and wirelessnetworks, and more particularly to apparatus, systems, and methods forgenerating and handling an enhanced wake up signal (WUS).

BACKGROUND

Wireless communication systems are rapidly growing in usage. In recentyears, wireless devices such as smart phones and tablet computers havebecome increasingly sophisticated. In addition to supporting telephonecalls, many mobile devices now provide access to the internet, email,text messaging, and navigation using the global positioning system(GPS), and are capable of operating sophisticated applications thatutilize these functionalities. Additionally, there exist numerousdifferent wireless communication technologies and standards. Someexamples of wireless communication standards include GSM, UMTS(associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE,LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD,eHRPD), IEEE 802.11 (WLAN or Wi-Fi), BLUETOOTH™, etc.

The ever increasing number of features and functionality introduced inwireless communication devices also creates a continuous need forimprovement in both wireless communications and in wirelesscommunication devices. To increase coverage and better serve theincreasing demand and range of envisioned uses of wirelesscommunication, in addition to the communication standards mentionedabove, there are further wireless communication technologies underdevelopment, including fifth generation (5G) new radio (NR)communication. Accordingly, improvements in the field in support of suchdevelopment and design are desired.

SUMMARY

Aspects relate to apparatuses, systems, and methods for power saving,comprising: establishing a radio resource control (RRC) connection witha wireless device; transmitting, to the wireless device, configurationinformation indicating a discontinuous reception (DRX) cycle time, a DRXon time period, and an offset time; transmitting an enhanced wake-upsignal (EWUS) monitoring occasion for a DRX cycle, the EWUS monitoringoccasion based on the offset time and the DRX on time period;determining that the wireless device can skip monitoring one or morefuture EWUS monitoring occasions; transmitting, during a first DRXcycle, an EWUS for the wireless device during the EWUS monitoringoccasion associated with the first DRX cycle, the EWUS indicating thatthe wireless device can skip the one or more future EWUS monitoringoccasions, and skipping transmitting the EWUS to the wireless deviceduring the one or more future WUS monitoring occasions.

Another aspect relates to apparatuses, systems, and methods for powersaving comprising: establishing a radio resource control (RRC)connection with a wireless system, entering an RRC connected mode basedon the established RRC connection, receiving, from the wireless system,configuration information indicating a discontinuous reception (DRX)cycle time, a DRX on time period, and an offset time, determining awake-up signal (WUS) monitoring occasion for a DRX cycle based on theoffset time and the DRX on time period, monitoring, during a first DRXcycle, for a WUS during the WUS monitoring occasion associated with thefirst DRX cycle, receiving, from the wireless system, the WUS during theWUS monitoring occasion, determining that the WUS indicates that thewireless device skip one or more future WUS monitoring occasions, andskipping monitoring for the WUS based on the indicated skipped one ormore future WUS monitoring occasions.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tocellular phones, wireless devices, tablet computers, wearable computingdevices, portable media players, and any of various other computingdevices.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various aspects is consideredin conjunction with the following drawings, in which:

FIG. 1 illustrates an example wireless communication system, accordingto some aspects;

FIG. 2 illustrates a base station (BS) in communication with a userequipment (UE) device, according to some aspects;

FIG. 3 illustrates an example block diagram of a UE, according to someAspects;

FIG. 4 illustrates an example block diagram of a BS, according to someaspects;

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some aspects;

FIG. 6 illustrates an example block diagram of a network element,according to some aspects;

FIG. 7 is a timing diagram illustrating receiving a physical downlinkcontrol channel (PDCCH) based on a WUS, in accordance with aspects ofthe present disclosure.

FIG. 8 is a timing diagram illustrating a first WUS skip mode ofoperation, in accordance with aspects of the present disclosure.

FIG. 9 is a timing diagram illustrating a first WUS skip mode ofoperation, in accordance with aspects of the present disclosure.

FIG. 10 is a timing diagram illustrating a second WUS skip mode ofoperation, in accordance with aspects of the present disclosure.

FIGS. 11A and 11B illustrate a technique for power saving for a wirelessdevice, in accordance with aspects of the present disclosure.

FIGS. 12A and 12B illustrate a technique for power saving, by a wirelessnode, in accordance with aspects of the present disclosure.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific aspects thereof are shownby way of example in the drawings and are herein described in detail. Itshould be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION

In some wireless communications systems, a wireless device maysuccessfully connect to a wireless node and enter an RRC connectedstate. In this RRC connected state, the wireless device may monitor aphysical downlink control channel (PDCCH) to obtain control information,scheduling information, paging information, etc. Rather than constantlymonitoring for the PDCCH, power consumption may be reduced by monitoringfor the PDCCH according to a schedule during defined monitoringinstances. Power consumption may be further reduced by allowing thewireless device to skip some scheduled PDCCH monitoring instances. Insome cases, a wake-up signal (WUS) may be used to indicate that awireless device should monitor an upcoming PDCCH monitoring instance.However, monitoring for a WUS uses more power than not monitoring forthe WUS, and there is a desire to reduce power consumption for wirelessdevices.

As will be explained further herein, an enhanced WUS may be used toindicate that one or more WUS monitoring instances may be skipped.

The following is a glossary of terms that may be used in thisdisclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such s electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays). PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs), The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic.”

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems or devices that are mobile or portable and that perform wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™,iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication.

Wireless Device—any of various types of computer systems or devices thatperform wireless communications. A wireless device can be portable (ormobile) or may be stationary or fixed at a certain location. A UE is anexample of a wireless device.

Communication Device—any of various types of computer systems or devicesthat perform communications, where the communications can be wired orwireless. A communication device can be portable (or mobile) or may bestationary or fixed at a certain location. A wireless device is anexample of a communication device. A UE is another example of acommunication device.

Base Station—The term “base station” or “wireless station” has the fullbreadth of its ordinary meaning, and at least includes a wirelesscommunication station installed at a fixed location and used tocommunicate as part of a wireless telephone system or radio system. Forexample, if the base station is implemented in the context of LTE, itmay alternately be referred to as an ‘eNodeB’ or ‘eNB’. If the basestation is implemented in the context of 5G NR, it may alternately bereferred to as a ‘gNodeB’ or ‘gNB’. Although some aspects are describedin the context of LTE or 5G NR, references to “eNB,” “gNB,” “nodeB,”“base station,” “NB,” etc., may refer to one or more wireless nodes thatservice a cell to provide a wireless connection between user devices anda wider network generally and that the concepts discussed are notlimited to any particular wireless technology. Although some aspects aredescribed in the context of LTE or 5G NR, references to “eNB,” “gNB,”“nodeB,” “base station,” “NB,” etc., are not intended to limit theconcepts discussed herein to any particular wireless technology and theconcepts discussed may be applied in any wireless system.

Node—The term “node,” or “wireless node” as used herein, may refer toone more apparatus associated with a cell that provide a wirelessconnection between user devices and a wired network generally.

Processing Element (or Processor)—refers to various elements orcombinations of elements that are capable of performing a function in adevice, such as a user equipment or a cellular network device.Processing elements may include, for example: processors and associatedmemory, portions or circuits of individual processor cores, entireprocessor cores, individual processors, processor arrays, circuits suchas an ASIC (Application Specific Integrated Circuit), programmablehardware elements such as a field programmable gale array (FPGA), aswell my of various combinations of the above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some aspects, “approximately” may mean within0.1% of some specified or desired value, while in various other aspects,the threshold may be, for example, 2%, 3%, 5%, and so forth, as desiredor as required by the particular application.

Concurrent—refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency may be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Configured to—Various components may be described as “configured to”perform a task or tasks. In such contexts, “configured to” is a broadrecitation generally meaning “having structure that” performs the taskor tasks during operation. As such, the component can be configured toperform the task even when the component is not currently performingthat task (e.g., a set of electrical conductors may be configured toelectrically connect a module to another module, even when the twomodules are not connected). In some contexts, “configured to” may be abroad recitation of structure generally meaning “having circuitry that”performs the task or tasks during operation. As such, the component canbe configured to perform the task even when the component is notcurrently on. In general, the circuitry that forms the structurecorresponding to “configured to” may include hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

Example Wireless Communication System

Turning now to FIG. 1 , a simplified example of a wireless communicationsystem is illustrated, according to some aspects. It is noted that thesystem of FIG. 1 is merely one example of a possible system, and thatfeatures of this disclosure may be implemented in any of varioussystems, as desired.

As shown, the example wireless communication system includes a basestation 102A, which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LIE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station in102A is implemented in the context of 5G NR, it may alternately bereferred to as a ‘gNodeB’ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1 , each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations which may be referred to as “neighboring cells.”Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some aspects, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB.” In someaspects, a gNB may be connected to a legacy evolved packet core (EPC)network and/or to a NR core (NRC)/5G core (5GC) network. In addition, agNB cell may include one or more transition and reception points (TRPs).In addition, a UE capable of operating according to 5G NR may beconnected to one or more TRPs within one or more gNBs. For example, itmay be possible that that the base station 102A and one or more otherbase stations 102 support joint transmission, such that UE 106 may beable to receive transmissions from multiple base stations (and/ormultiple TRPs provided by the same base station). For example, asillustrated in FIG. 1 , both base station 102A and base station 102C areshown as serving UE 106A.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, HSDPA,HSUPA, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE106 may also or alternatively be configured to communicate using one ormore global navigational satellite systems (GNSS, e.g., GPS or GLONASS),one or more mobile television broadcasting standards (e.g., ATSC-M/H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

Example User Equipment (UE)

FIG. 2 illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102, according tosome aspects. The UE 106 may be a device with cellular communicationcapability such as a mobile phone, a hand-held device, a computer, alaptop, a tablet, a smart watch or other wearable device, or virtuallyany type of wireless device.

The UE 106 may include a processor (processing element) that isconfigured to execute program instructions stored in memory. The UE 106may perform any of the method aspects described herein by executing suchstored instructions. Alternatively, or in addition, the UE 106 mayinclude a programmable hardware element such as an FPGA(field-programmable gate array), an integrated circuit, and/or any ofvarious other possible hardware components that are configured toperform (e.g., individually or in combination) any of the method aspectsdescribed herein, or any portion of any of the method aspects describedherein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies, In someaspects, the UE 106 may be configured to communicate using, for example,NR or LTE using at least some shared radio components. As additionalpossibilities, the UE 106 could be configured to communicate usingCDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD) or LTE using a single shared radioand/or GSM or LTE using the single shared radio. The shared radio maycouple to a single antenna, or may couple to multiple antennas (e.g.,for MIMO) for performing wireless communications. In general, a radiomay include any combination of a baseband processor, analog RF signalprocessing circuitry (e.g., including filters, mixers, oscillators,amplifiers, etc.), or digital processing circuitry (e.g., for digitalmodulation as well as other digital processing). Similarly, the radiomay implement one or more receive and transmit chains using theaforementioned hardware. For example, the UE 106 may share one or moreparts of a receive and/or transmit chain between multiple wirelesscommunication technologies, such as those discussed above.

In some aspects, the UE 106 may include separate transmit and/or receivechains (e.g., including separate antennas and other radio components)for each wireless communication protocol with which it is configured tocommunicate. As a further possibility, the UE 106 may include one ormore radios which are shared between multiple wireless communicationprotocols, and one or more radios which are used exclusively by a singlewireless communication protocol. For example, the UE 106 might include ashared radio for communicating using either of LTE or 5G NR (or eitherof LTE or 1×RTT, or either of LTE or GSM, among various possibilities),and separate radios for communicating using each of Wi-Fi and Bluetooth.Other configurations are also possible.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the base stations 102 to the UEs 106, whileuplink transmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. Thesmallest time-frequency unit in a resource grid is denoted as a resourceelement. Each resource grid may comprise a number of resource blocks,which describe the mapping of certain physical channels to resourceelements. Each resource block comprises a collection of resourceelements. There are several different physical downlink channels thatare conveyed using such resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 106. The physical downlink controlchannel (PDCCH) may carry information about the transport format andresource allocations related to the PDSCH channel, among other things.It may also inform the UEs 106 about the transport format, resourceallocation, and H-ARQ (Hybrid Automatic Repeat Request) informationrelated to the uplink shared channel. Typically, downlink scheduling(assigning control and shared channel resource blocks to the UE 102within a cell) may be performed at any of the base stations 102 based onchannel quality information fed back from any of the UEs 106. Thedownlink resource assignment information may be sent on the PDCCH usedfor (e.g., assigned to) each of the UEs.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Example Communication Device

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some aspects. It is noted thatthe block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to aspects,communication device 106 may be a user equipment (UE) device, a mobiledevice or mobile station, a wireless device or wireless station, adesktop computer or computing device, a mobile computing device (e.g., alaptop, notebook, or portable computing device), a tablet, and/or acombination of devices, among other devices. As shown, the communicationdevice 106 may include a set of components 300 configured to performcore functions. For example, this set of components may be implementedas a system on chip (SOC), which may include portions for variouspurposes. Alternatively, this set of components 300 may be implementedas separate components or groups of components for the various purposes.The set of components 300 may be coupled (e.g., communicatively;directly or indirectly) to various other circuits of the communicationdevice 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andwireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, UMTS,GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.). In some aspects,communication device 106 may include wired communication circuitry (notshown), such as a network interface card, e.g., for Ethernet.

The wireless communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antenna(s) 335 as shown. The wireless communication circuitry 330 mayinclude cellular communication circuitry and/or short to medium rangewireless communication circuitry, and may include multiple receivechains and/or multiple transmit chains for receiving and/or transmittingmultiple spatial streams, such as in a multiple-input multiple output(MIMO) configuration.

In some aspects, as further described below, cellular communicationcircuitry 330 may include one or more receive chains (including and/orcoupled to (e.g., communicatively; directly or indirectly) dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someaspects, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be in dedicated to a first RAT,e.g., LTE, and may be in communication with a dedicated receive chainand a transmit chain shared with a second radio. The second radio may bededicated to a second RAT, e.g., 5G NR, and may be in communication witha dedicated receive chain and the shared transmit chain. In someaspects, the second RAT may operate at mmWave frequencies. As mmWavesystems operate in higher frequencies than typically found in LTEsystems, signals in the mmWave frequency range are heavily attenuated byenvironmental factors. To help address this attenuating, mmWave systemsoften utilize beamforming and include more antennas as compared LTEsystems. These antennas may be organized into antenna arrays or panelsmade up of individual antenna elements. These antenna arrays may becoupled to the radio chains.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, wireless communication circuitry 330, connectorI/F 320, and/or display 360. The MMU 340 may be configured to performmemory protection and page table translation or set up. In some aspects,the MMU 340 may be included as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Asdescribed herein, the communication device 106 may include hardware andsoftware components for implementing any of the various features andtechniques described herein. The processor 302 of the communicationdevice 106 may be configured to implement part or all of the featuresdescribed herein, e.g., by executing program instructions stored on amemory medium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processor 302 may be configured as aprogrammable hardware element, such as an FPGA (Field Programmable GateArray), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processor 302 of the communicationdevice 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 330, 340, 345, 350, 360 may be configured toimplement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, wireless communication circuitry 330 mayinclude one or more processing elements. In other words, one or moreprocessing elements may be included in wireless communication circuitry330. Thus, wireless communication circuitry 330 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof wireless communication circuitry 330. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of wireless communicationcircuitry 330.

Example Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some aspects. It is noted that the base station of FIG. 4is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2 .

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some aspects, base station 102 may be a next generation base station,e.g., a 5G New Radio (5G NR) base station, or “gNB.” In such aspects,base station 102 may be connected to a legacy evolved packet core (EPC)network and/or to a NR core (NRC)/5G core (5GC) network. In addition,base station 102 may be considered a 5G NR cell and may include one ormore transition and reception points (TRPs). In addition, a UE capableof operating according to 5G NR may be connected to one or more TRPswithin one or more gNBs.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430, The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. When the base station 102supports mmWave, the 5G NR radio may be coupled to one or more mmWaveantenna arrays or panels. As another possibility, the base station 102may include a multi-mode radio, which is capable of performingcommunications according to any of multiple wireless communicationtechnologies (e.g., 5G NR and LTE, 5G NR and Wi-Fi, LIE and Wi-Fi, LIEand UMTS, LIE and CDMA2000, UNITS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may include one ormore processing elements. Thus, processor(s) 404 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor(s) 404. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 404.

Further, as described herein, radio 430 may include one or moreprocessing elements. Thus, radio 430 may include one or more integratedcircuits (ICs) that are configured to perform the functions of radio430. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of radio 430.

Example Cellular Communication Circuitry

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some aspects. It is noted that theblock diagram of the cellular communication circuitry of FIG. 5 is onlyone example of a possible cellular communication circuit; othercircuits, such as circuits including or coupled to sufficient antennasfor different RATs to perform uplink activities using separate antennas,or circuits including or coupled to fewer antennas, e.g., that may beshared among multiple RATs, are also possible. According to someaspects, cellular communication circuitry 330 may be included in acommunication device, such as communication device 106 described above.As noted above, communication device 106 may be a user equipment (UE)device, a mobile device or mobile station, a wireless device or wirelessstation, a desktop computer or computing device, a mobile computingdevice (e.g., a laptop, notebook, or portable computing device), atablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown. In some aspects, cellularcommunication circuitry 330 may include dedicated receive chains(including and-'or coupled to (e.g., communicatively; directly orindirectly) dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5 , cellular communication circuitry 330 mayinclude a first modem 510 and a second modem 520. The first modem 510may be configured for communications according to a first RAT, e.g.,such as LTE or LTE-A, and the second modem 520 may be configured forcommunications according to a second RAT, e.g., such as 5G NR.

As shown, the first modem 510 may include one or more processors 512 anda memory 516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals,For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some aspects, receive circuitry 532 maybe in communication with downlink (DL) front end 550, which may includecircuitry for receiving radio signals via antenna 335 a.

Similarly, the second modem 520 may include one or more processors 522and a memory 526 in communication with processors 522. Modem 520 may bein communication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some aspects, receive circuitry 542 may be in communication withDL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some aspects, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via the first modem 510),switch 570 may be switched to a first state that allows the first modem510 to transmit signals according to the first RAT (e.g., via a transmitchain that includes transmit circuitry 534 and UL front end 572).Similarly, when cellular communication circuitry 330 receivesinstructions to transmit according to the second RAT (e.g., as supportedvia the second modem 520), switch 570 may be switched to a second statethat allows the second modem 520 to transmit signals according to thesecond RAT (e.g., via a transmit chain that includes transmit circuitry544 and UL front end 572).

As described herein, the first modem 510 and/or the second modem 520 mayinclude hardware and software components for implementing any of thevarious features and techniques described herein, The processors 512,522 may be configured to implement part or all of the features describedherein, e.g., by executing program instructions stored on a memorymedium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processors 512, 522 may be configured asa programmable hardware element, such as an FPGA (Field ProgrammableGate Army), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processors 512, 522, in conjunctionwith one or more of the other components 530, 532, 534, 540, 542, 544,550, 570, 572, 335 and 336 may be configured to implement part or all ofthe features described herein.

In addition, as described herein, processors 512, 522 may include one ormore processing elements. Thus, processors 512, 522 may include one ormore integrated circuits (ICs) that are configured to perform thefunctions of processors 512, 522. In addition, each integrated circuitmay include circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of processors 512, 522.

In some aspects, the cellular communication circuitry 330 may includeonly one transmit/receive chain. For example, the cellular communicationcircuitry 330 may not include the modem 520, the RF front end 540, theDL front end 560, and/or the antenna 335 b. As another example, thecellular communication circuitry 330 may not include the modem 510, theRF front end 530, the DL front end 550, and/or the antenna 335 a. Insome aspects, the cellular communication circuitry 330 may also notinclude the switch 570, and the RF front end 530 or the RF front end 540may be in communication, e.g., directly, with the UL, front end 572.

Example Network Element

FIG. 6 illustrates an exemplary block diagram of a network element 600,according to some aspects. According to some aspects, the networkelement 600 may implement one or more logical functions/entities of acellular core network, such as a mobility management entity (MME),serving gateway (S-GW), access and management function (AMF), sessionmanagement function (SMF), network slice quota management (NSQM)function, etc. It is noted that the network element 600 of FIG. 6 ismerely one example of a possible network element 600. As shown, the corenetwork element 600 may include processor(s) 604 which may executeprogram instructions for the core network element 600. The processor(s)604 may also be coupled to memory management unit (MMU) 640, which maybe configured to receive addresses from the processor(s) 604 andtranslate those addresses to locations in memory (e.g., memory 660 andread only memory (ROM) 650) or to other circuits or devices.

The network element 600 may include at least one network port 670. Thenetwork port 670 may be configured to couple to one or more basestations and/or other cellular network entities and/or devices, Thenetwork element 600 may communicate with base stations (e.g., eNBs/gNBs)and/or other network entities/devices by means of any of variouscommunication protocols and/or interfaces.

As described further subsequently herein, the network element 600 mayinclude hardware and software components for implementing and/orsupporting implementation of features described herein. The processor(s)604 of the core network element 600 may be configured to implement orsupport implementation of part or all of the methods described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a nontransitory computer-readable memory medium). Alternatively, theprocessor 604 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof.

Radio Resource Control (RRC) States

Multiple cellular communication technologies include the use of a radioresource control (RRC) protocol, e.g., which may facilitate connectionestablishment and release, radio bearer establishment, reconfiguration,and release, and/or various other possible signaling functionssupporting the air interface between a wireless device and a cellularbase station.

A wireless device may commonly operate in one of multiple possiblestates with respect to RRC. For example, in LTE, a wireless device mayoperate in an RRC connected state (e.g., in which the wireless devicecan perform continuous data transfer, and in which handover betweencells is managed by the network and access stratum (AS) contextinformation is retained for the wireless device), or in an RRC idlestate (e.g., in which the wireless device may operate in a more batteryefficient state when not performing continuous data transfer, in whichthe wireless device may handle it's cell re-selection activities, and inwhich the network may not retain AS context information for the wirelessdevice), in some cases, a wireless device may also operate in an RRCinactive state where the radio bearers with the network are suspended,but the AS context is still maintained by the wireless device and thewireless network, which helps enable quicker resumption back to the RRCconnected state.

In some cases, when the wireless device is in the RRC connected state,the wireless device may continually monitor for the PDCCH transmissionto the wireless device. Continually monitoring a channel can consume asubstantial amount of power. For example, the RF front end andcorresponding modem may need to remain powered on and one or moreprocessors may be used to attempt to decode transmissions whenmonitoring the channel. To help reduce an amount of power used bywireless device, discontinuous reception (DRX) may be implemented in theRRC connected state. Using DRX, a wireless device may receive, from thewireless network, a schedule for when the wireless device should monitorthe PDCCH and when the wireless device does not need to monitor thePDCCH. Together, an instance of time the wireless device should monitorthe PDCCH, referred to as an on-duration, and an instance of time thewireless devices does not need to monitor the PDCCH, referred to as anoff-duration, may be together comprise a DRX cycle. As the wirelessdevice does not need to monitor the PDCCH during the off-duration, thewireless device may enter a relatively low power state (e.g., sleep, orother lower power state) as compared to the on-duration. For example,the wireless device may partially or completely power down the RF frontend, modem, one or more processers, and/or other component that may beused to receive uplink transmissions during the off-duration. Whilemonitoring the PDCCH during DRX on-durations reduces power consumptionas compared to constantly monitoring the PDCCH, additional power savingscan be had by not monitoring, e.g., skipping, the PDCCH during certainDRX on-durations.

Turning now to FIG. 7 , a timing diagram 700 illustrating receiving aphysical downlink control channel (PDCCH) based on a WUS, in accordancewith aspects of the present disclosure. Timing diagram 700 illustratesrelationships between WUS 716 transmissions and PDCCH 718 transmissionsover multiple DRX cycles 704 on a time axis 702. As shown, the DRXcycles 704 includes a partial first DRX cycle which ends at time 706, asecond DRX cycle starts at time 706 and ends at time 708, and a thirdDRX cycle starts at time 708 and ends at time 710. The second DRX cycleand third DRX cycles include an on-duration 712 and an off-duration 714,while the first DRX cycle includes an off-duration 714. It may beunderstood that the first DRX cycle may include an on-duration 712, butthe on-duration 712 may have occurred prior to the time periodillustrated in FIG. 7 . In some cases, a wireless device may beconfigured to monitor for a WUS 716 transmitted by a wireless node priorto an on-duration 712 in which a PDCCH 718 may be transmitted. In thisexample, WUS 716A may be associated with and transmitted prior to PDCCH718A during a time offset 720 prior to an on-duration 712A associatedwith the PDCCH 718A. If the wireless device receives the WUS 716A, thewireless device may monitor for the PDCCH 718A during the on-duration712A. This process may be repeated for each DRX cycle. For example, thewireless device may monitor during a time offset 720 prior to onduration 712B for a WUS. If the wireless device does not receive the WUS(e.g., a skipped WUS 724A), the wireless device may not monitor for thePDCCH (e.g., a skipped PDCCH 722A) in the next on-duration 712B. Forexample, the wireless device may not start an on-duration timer duringthe next on-duration 712B (e.g., monitoring occasion for the PDCCH). Thewireless device may enter or remain in a sleep or lower power state forall or a portion of the next on-duration 712B. The wireless device thenrepeats this process, monitoring for another WUS during a time offset720 prior to another on-duration, and so forth.

A wireless device may receive, for example from a wireless node, aconfiguration message which configures connected mode DRX. In somecases, a configuration message may be received by a wireless device froma wireless network via a radio resource control (RRC) message. Theconfiguration message may define the DRX cycles 704, for example, byproviding DRX cycles 704 timing information. In some cases, theconfiguration message may also include information about a WUS 716. Forexample, the configuration message may indicate a time offset 718 fromthe start of a DRX on-duration 712. The time offset 718 may define a WUSmonitoring occasion time period prior to the DRX on-duration 712 inwhich the wireless device may monitor for the WUS 716 signal. In somecases, the time offset 720 may have a predefined duration. In othercases, the time offset 720 may have a configurable duration, forexample, as indicated in the configuration message.

in some cases, the WUS 716 may be a relatively short and simple signalas compared to the PDCCH 718. In some cases, a wireless device may havea dedicated, simplified, receiver for receiving the WUS 716 while usingless power than a receiver for receiving the PDCCH 718. In some cases, awireless device may use the same receiver for receiving the WUS 716 andPDCCH 718, but may be able to reduce an amount of power consumed by thereceiver when receiving the WUS 716, for example by turning off someportions of the receiver, processor, etc. While monitoring for the WUS716 during a prescribed interval can reduce power consumption ascompared to monitoring for the PDCCH 718 during a prescribed interval,additional power savings may be obtained if the wireless device couldskip monitoring for the WUS 716 during one or more WUS monitoringoccasions. Skipping the WUS transmission may benefit the wirelessnetwork. For example, the wireless node may be able to use the skippedWUS monitoring occasions to service other wireless devices,

In accordance with aspects of the present disclosure, a WUS may beenhanced (e.g., EWUS) by adding additional information to the WUS toindicate to the UE whether the UE can skip monitoring for the WUS in afuture WUS monitoring occasion. In some cases, a WUS signal may betransmitted as a DCI message, such as a DCI format 2_6 message, and bitsmay be added to the DCI message, indicating whether future WUSmonitoring occasions may be skipped and if so, how many future WUSmonitoring occasions may be skipped. For example, a single bit may beadded to indicate whether to allow WUS monitoring occasions to beskipped, and a second bit may be added to indicate how many WUSmonitoring occasions may be skipped. In some cases, there may be one ormore WUS skip modes of operation.

For example, in a first enhanced WUS skip mode of operation, thewireless device may determine that the wireless device can skip one ormore future WUS monitoring occasions while monitoring for the PDCCHmessages associated with the one or more skipped WUSs. In the first WUSskip mode, a single WUS can indicate that the wireless device shouldmonitor for multiple PDCCH messages, but that it may skip monitoring forthe WUS associated with those multiple PDCCH messages.

FIG. 8 is a timing diagram 800 illustrating a first WUS skip mode ofoperation, in accordance with aspects of the present disclosure, Timingdiagram 800 also illustrates relationships between WUS 816 transmissionsand PDCCH 818 transmissions over multiple DRX cycles 804A-804F on a timeaxis 802. In timing diagram 800, DRX on and off durations as well asmonitoring intervals, as compared to FIG. 7 , have been omitted forclarity.

In some cases, a WUS skip value may be encoded into the WUS 816indicating whether or how many WUS monitoring occasions may be skipped.For example, the WUS skip value may be a bit added to the WUS 816indicating whether the wireless device may skip a WUS monitoringoccasion. In some cases, a WUS skip value of 0 may indicate that thewireless device may not skip a WUS monitoring occasion. In such casesthe wireless device may then monitor for a PDCCH during the nexton-duration and monitor for another WUS during the next WUS monitoringoccasion, as discussed above with respect to FIG. 7 . In some cases, aWUS skip value of 1 may indicate that the wireless device may skip anext WUS monitoring occasion. For example, a wireless node may determinethat it needs to transmit multiple PDCCH messages to the to the wirelessdevice over multiple DRX cycles, such as if the wireless device issending or receiving data over a period of time. The wireless node maythen transmit a first WUS 816A during a WUS monitoring occasion to thewireless device with an encoded skip value of 1. The wireless device mayreceive the first WUS 816A during the WUS monitoring occasion and decodethe WUS. Where the WUS skip value is one, the wireless device maydetermine that the wireless device may skip one WUS monitoring occasionand monitor for one additional PDCCH occasion in addition to the nextPDCCH monitoring occasion. For example, the UE may monitor for a firstPDCCH 818A during the next on-duration in a second DRX cycle 804B aswell as a second PDCCH 818B during the on-duration in a third DRX cycle804C (e.g., the on-duration right after the next on-duration), withoutmonitoring for skipped WUS 824B. After skipping WUS 824B, the wirelessdevice may resume monitoring for a WUS during the next WUS interval andreceive a second WUS 816B. This second WUS 816B may also include a WUSskip value of 1 the wireless device may skip monitoring for skipped WUS824C while monitoring for PDCCH 8180 and 818D. In some cases, if thewireless device does not receive the WUS, such as skipped WUS 824A in afifth DRX cycle 804E, the wireless device may operate as described abovewith respect in FIG. 7 and not monitor for the PDCCH, such as skippedPDCCH 822 in a sixth DRX cycle 804F.

In some cases, the first WUS skip mode may be extended to supportskipping additional WUS monitoring occasions. In some cases, the WUSskip value may represent a number of WUS monitoring occasions that maybe skipped. For example, as discussed above, a WUS skip value of 0 mayindicate that the wireless device should not skip a WUS monitoringoccasion, while a WUS skip value of 1 may indicate that the wirelessdevice may skip one WUS monitoring occasion. In some cases, higher WUSskip values may be treated similarly. For example, a second bit may beadded to a WUS, enabling up to 4 values (e.g., 3) to be encoded in theWUS skip value.

FIG. 9 is a timing diagram 900 illustrating a first WUS skip mode ofoperation, in accordance with aspects of the present disclosure. In FIG.9 , a wireless device may receive a first WUS 916A during the WUSmonitoring occasion and decode the first WUS 916A. In this example, theWUS skip value is two, and the wireless device may determine that thewireless device may skip monitoring for two skipped WUS 924A, 924B inDRX cycles 904B and 904C, respectively, and monitor for two additionalPDCCH 918B, 918C in DRX cycles 904C and 904D, respectively, in additionto monitoring for the next PDCCH 918A in DRX cycle 904B. In some cases,if the wireless device does not receive the WUS, such as skipped WUS924C in a fourth DRX cycle 804D, the wireless device may operate asdescribed above with respect in FIGS. 7 and 8 and not monitor for thePDCCH, such as skipped PDCCH 922 in a fifth DRX cycle 904E. Similarly,if the WUS skip value is three, the wireless device may skip monitoringfor three skipped WUS monitoring occasions and monitor for threeadditional PDCCH monitoring occasions in addition to monitoring in thenext PDCCH monitoring occasion. In some cases, a number of skipped WUSmonitoring occasions may be limited as it may be difficult for awireless node to accurately schedule that far in advance. For example,the number of skipped WUS monitoring occasions may be limited to 3.

In some cases, in a second WUS skip mode of operation, the wirelessdevice may determine that the wireless device can skip one or morefuture WUS monitoring occasions along with the PDCCH monitoringoccasions associated with the one or more skipped WUS monitoringoccasions. This mode of operation may be useful if a wireless nodedetermines that the wireless device does not need to send or receivedata for a period of time. For example, a wireless node may determinethat a wireless device is sending or receiving data periodically withrelatively large gaps between transmissions, or the wireless node mayhave multiple, relatively small sets of non-time critical data for awireless device, the wireless node may batch up the data and send thedata to the wireless device all together. By reducing a number oftransmissions, the wireless device may be able to reduce an amount ofpower consumption and stay in a lower power state longer.

In some cases, in this second WUS skip mode of operation, a WUS skipvalue may also be encoded into the WUS. In a manner similar to thatdiscussed in conjunction with FIGS. 7 and 8 and the first WUS skip modeof operation, the WUS skip value may be encoded as one or two bits inthe WUS. In some cases, a WUS skip value of 0 may indicate that thewireless device may not skip a WUS monitoring occasion. In some cases, aWUS skip value of one may indicate that the wireless device may skip oneWUS monitoring occasion along with an associated PDCCH monitoringoccasion. Similarly, a WUS skip value of two or three may indicate thatthe wireless device may skip a corresponding number of WUS monitoringoccasions along with the respective, associated, PDCCH monitoringoccasions.

FIG. 10 is a timing diagram 1000 illustrating a second WUS skip mode ofoperation, in accordance with aspects of the present disclosure. In afirst example in FIG. 10 , a wireless device may receive and decode afirst WUS 1016A in a first DRX cycle 1004A to determine that the WUSskip value is one. The wireless device may then determine that thewireless device may not monitor for a skipped WUS 1024A in a second DRXcycle 1004B. The wireless device may also not monitor for skipped PDCCH1022A in a third DRX cycle 1004C associated with the skipped WUS 1024A.The wireless device may still monitor for the next PDCCH 1018A in thesecond DRX cycle 1004B associated with the first WUS 1016A.

In another example in FIG. 10 , the wireless device may decode a secondWUS 1016B in a third DRX cycle 1004C to determine that the WUS skipvalue is two. The wireless device may then determine that the wirelessdevice may not monitor for two WUS monitoring occasions, such as skippedWUS 1024B and 1024C. The wireless device may also not monitor for twoskipped PDCCH 1022B and 1022C associated with skipped WUS 1024B and1024C, respectively. Similarly, if the WUS skip value is three, thewireless device may skip monitoring for three skipped WUS monitoringoccasions and monitor for three additional PDCCH monitoring occasions inaddition to monitoring in the next PDCCH monitoring occasion. In somecases, additional bits may be added to allow for any number of WUS skipvalues to be specified. In some cases, the number of WUS skip values maybe limited, such as to three WUS monitoring occasions, due to schedulinglimitations.

In some cases, the WUS may include an indication of which WUS skip modeof operation to use. For example, the WUS may include a bit indicatingwhether the wireless device may operate under the first WUS skip mode,or the second WUS skip mode of operation. In some cases, the WUS skipmode of operation may be signaled to the wireless device using signalingdifferent from the WUS. For example, the WUS skip mode may be indicatedin a configuration message or dedicated signaling, such as a MAC CE orbroadcast signaling for UEs associated with one or more wireless nodes.

In some cases, specific behaviors may be mapped to values of the WUSskip value. For example, WUS skip values may be mapped to one or morepatterns for skipping WUS monitoring occasions, such as skipping everyother monitoring occasion until changed. As another example, a defaultWUS skip value may be predefined, such as in a specification, and thedefault WUS skip value may be applied when no skip value is provided, orthe default WUS skip value may always applied.

In some cases, the enhanced WUS may also be applied in the RRC idle andRRC inactive modes. For example, in the RRC inactive/idle modes, thewireless node may indicate, to the wireless device, a paging interval(e.g., a DRX cycle for paging). Further, the wireless device may beconfigured with a WUS monitoring occasion prior to the paging interval.The wireless node may transmit an enhanced WUS and indicate whether thewireless device can skip one or more future WUS monitoring occasions ina manner similar to that discussed above in conjunction with FIGS. 8-10. Similarly, the enhanced WUS may indicate whether the wireless devicemay skip or more future paging intervals in a manner similar to thatdiscussed above in conjunction with FIG. 10 .

FIGS. 11A and 11B illustrate a technique for power saving for a wirelessdevice, in accordance with aspects of the present disclosure. In FIG.11A, exemplary wireless device behaviors 1100 are described. At step1102, a radio resource control (RRC) connection with a wireless systemmay be established. At step 1104, an RRC connected mode may be enteredbased on the established RRC connection. For example, a wireless devicemay establish an RRC connection with a wireless node and the wirelessmode may enter an RRC connected mode. In some cases, step 1102 and step1104 may be optional. For example, the wireless device may be in an RRCidle mode. As another example, the wireless device may have establishedan RRC connection with the wireless system, but is in an RRC inactivemode. At step 1106, configuration information may be received from thewireless node indicating a discontinuous reception (DRX) cycle time, aDRX on time period, and an offset time. For example, the wireless devicemay receive a configuration message including information defining a DRXcycle and WUS timing information. At step 1108, a WUS monitoringoccasion may be determined for a DRX cycle based on the offset time andthe DRX on time period. For example, a WUS monitoring occasion may bedetermined based on the offset time from the DRX on-duration. At step1110, the wireless device may monitor, during a first DRX cycle, for aWUS during the WUS monitoring occasion associated with the first DRXcycle. For example, the wireless device may monitor for a WUS during afirst WUS monitoring occasion. At step 1112, the wireless device mayreceive, from the wireless system, the WUS during the WUS monitoringoccasion. For example, the wireless device may receive a DCI messageindicating that the wireless device should monitor the PDCCH during anext PDCCH monitoring occasion. At step 1114, the wireless device maydetermine that the WUS indicates that the wireless device skip one ormore future WUS monitoring occasions. For example, the WUS may includean encoded WUS skip value indicating that the wireless device may skipone or more WUS monitoring occasions. At step 1116, the wireless devicemay skip monitoring for the WUS based on the indicated skipped one ormore future WUS monitoring occasions.

FIG. 11B describes optional behaviors of the exemplary wireless devicebehaviors 1100. At step 1120, the WUS may indicate that the wirelessdevice skip one or more WUS monitoring occasions and PDCCH monitoringinstances associated with the one or more WUS monitoring occasions. Forexample, in the second WUS skip mode of operation, the wireless devicemay skip one or more WUS monitoring occasions. The wireless device mayalso skip one or more PDCCH monitoring occasions associated with theskipped one or more WUS monitoring occasions. At step 1122, the WUS mayindicate that the wireless device skip one or more WUS monitoringoccasions associated with the one or more WUS monitoring occasions. Forexample, in the first WUS skip mode of operation, the wireless devicemay skip one or more WUS monitoring occasions. In some cases, for eitherthe first or second WUS skip mode of operation, the WUS may include anencoded value indicating a number of WUS monitoring occasions to skip.In some cases, the WUS may include an indication whether to skipmonitoring a PDCCH instance associated with a WUS monitoring occasion.

FIGS. 12A and 12B illustrate a technique for power saving, by a wirelessnode, in accordance with aspects of the present disclosure. In FIG. 12A,exemplary wireless node behaviors 1200 are described. At step 1202, aradio resource control (RRC) connection with a wireless device may beestablished. For example, a wireless device may establish an RRCconnection with the wireless node and the wireless device may enter anRRC connected mode. At step 1204, configuration information may betransmitted to the wireless node indicating a discontinuous reception(DRX) cycle time, a DRX on time period, and an offset time. For example,the wireless node may determine a DRX cycle and WUS timing informationfor the wireless device. At step 1206, a wake-up signal (WUS) monitoringoccasion for a DRX cycle, the WUS based on the offset time, and the DRXon time period may be transmitted to the wireless device. For example,the wireless node may transmit a configuration message indicating thedetermined DRX cycle and WUS timing information to the wireless device.At step 1208, a determination may be made that the wireless device canskip monitoring one or more future WUS monitoring occasions. Forexample, the wireless node may determine that the wireless node has datato transmit to the wireless device in two or more PDCCH messages. Thewireless node may determine a number of PDCCH messages to use, forexample based on an amount of data to transmit. The number of future WUSmonitoring occasions that may be skipped may be based on the number ofPDCCH messages. As another example, the wireless node may determine notto transmit a number of PDCCH messages to the wireless device. Thenumber of future WUS monitoring occasions that may be skipped may bebased on the determined number of PDCCH messages not to transmit.

At step 1210, during a first DRX cycle, a WUS for the wireless devicemay be transmitted during the WUS monitoring occasion associated withthe first DRX cycle, the WUS indicating that the wireless device canskip the one or more future WUS monitoring occasions. For example, theWUS may be transmitted as a DCI message. In some cases, the WUS may alsoindicate whether to skip monitoring a PDCCH instance associated with aWUS monitoring occasion. In some cases, the WUS includes an encodedvalue indicating a number of WUS monitoring occasions and PDCCHmonitoring instances associated with the multiple WUS monitoringoccasions based on a pattern. At step 1212, transmitting the WUS to thewireless device during the one or more future WUS monitoring occasionsmay be skipped.

FIG. 12B describes optional behaviors of the exemplary wireless nodebehaviors 1200. At step 1220, the wireless node may determine that thewireless node has data to transmit to the wireless device in two or morePDCCH messages. For example, the wireless node may have data for thewireless device that requires multiple PDCCH messages to transmit. Thewireless node may, for example in the first WUS skip mode of operation,indicate to the wireless device to skip one or more WUS monitoringoccasions while still monitoring multiple PDCCH monitoring occasions. Atstep 1222, the wireless node determines a number of PDCCH messages totransmit. At step 1224, the wireless node may determine not to transmita number of PDCCH messages to the wireless device. For example, thewireless node may determine that a that the wireless device can skip oneor more future WUS monitoring occasions along with the PDCCH monitoringoccasions associated with the one or more skipped WUS monitoringoccasions.

Note that dashed lines around boxes and dashed arrows in FIGS. 11B and12B

EXAMPLES

In the following sections, further exemplary aspects are provided.

According to Example 1, a method for power saving for a wireless device,comprising: establishing a radio resource control (RRC) connection witha wireless system; entering an RRC connected mode based on theestablished RRC connection; receiving, from the wireless system,configuration information indicating a discontinuous reception (DRX)cycle time, a DRX on time period, and an offset time; determining anenhanced wake-up signal (EWUS) monitoring occasion for a DRX cycle basedon the offset time and the DRX on time period; monitoring, during afirst DRX cycle, for an EWUS during the EWUS monitoring occasionassociated with the first DRX cycle; receiving, from the wirelesssystem, the EWUS during the EWUS monitoring occasion; determining thatthe EWUS indicates that the wireless device skip one or more future EWUSmonitoring occasions; and skipping monitoring for the EWUS based on theindicated skipped one or more future EWUS monitoring occasions.

Example 2 comprises the subject matter of example 1 and furthercomprises: determining the EWUS indicates that the wireless devicemonitor a physical downlink control channel (PDCCH) instance in a nextDRX cycle, wherein the PDCCH instance is associated with the EWUSmonitoring occasion; and monitoring the PDCCH instance in the next DRXcycle based on the EWUS.

Example 3 comprises the subject matter of example 2 and furthercomprises skipping monitoring a PDCCH instance associated with a nextEWUS monitoring occasion.

Example 4 comprises the subject matter of example 1, wherein the EWUSindicates that the wireless device skip multiple EWUS monitoringoccasions and PDCCH monitoring instances associated with the multipleEWUS monitoring occasions, and wherein skipping monitoring comprisesskipping monitoring for the EWUS in multiple DRX cycles based on theEWUS.

Example 5 comprises the subject matter of example 4, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 6 comprises the subject matter of example 5, wherein the encodedvalue is encoded in two bits of a downlink control message.

Example 7 comprises the subject matter of example 1, wherein the EWUSindicates that the wireless device skip multiple EWUS monitoringoccasions, and wherein skipping monitoring comprises skipping monitoringfor the EWUS in multiple DRX cycles based on the EWUS.

Example 8 comprises the subject matter of example 7 and furthercomprising: determining the EWUS indicates that the wireless devicemonitor physical downlink control channel (PDCCH) instances in themultiple DRX cycles; and monitoring the PDCCH instances in the multipleDRX cycles based on the indication based on the EWUS.

Example 9 comprises the subject matter of example 7, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 10 comprises the subject matter of example 1, wherein the EWUSindicates whether to skip monitoring a PDCCH instance associated with aEWUS monitoring occasion.

Example 11 comprises the subject matter of example 1, wherein the EWUSis transmitted in a downlink control message.

Example 12 comprises the subject matter of example 1, wherein the EWUSis associated with a predetermined default number of EWUS monitoringoccasions to skip,

According to Example 13, a method for power saving for a wirelessdevice, comprising: receiving, from the wireless system, configurationinformation indicating a discontinuous reception (DRX) cycle time, a DRXon time period, and an offset time; determining an enhanced wake-upsignal (EWUS) monitoring occasion for a DRX cycle based on the offsettime and the DRX on time period; monitoring, during a first DRX cycle,for an EWUS during the EWUS monitoring occasion associated with thefirst DRX cycle; receiving, from the wireless system, the EWUS duringthe EWUS monitoring occasion; determining that the EWUS indicates thatthe wireless device skip one or more future EWUS monitoring occasions;and skipping monitoring for the EWUS based on the indicated skipped oneor more future EWUS monitoring occasions.

Example 14 comprises the subject matter of example 13, wherein thewireless device is in an RRC idle mode.

Example 15 comprises the subject matter of example 13, wherein thewireless device is in an RRC inactive mode.

According to Example 16, a wireless device comprising: an antenna; aradio operably coupled to the antenna; and a processor operably coupledto the radio; wherein the wireless device is configured to: establish aradio resource control (RRC) connection with a wireless system; enter anRRC connected mode based on the established RRC connection; receive,from the wireless system, configuration information indicating adiscontinuous reception (DRX) cycle time, a DRX on time period, and anoffset time; determine an enhanced wake-up signal (EWUS) monitoringoccasion for a DRX cycle based on the offset time and the DRX on timeperiod; monitor, during a first DRX cycle, for an EWUS during the EWUSmonitoring occasion associated with the first DRX cycle; receive, fromthe wireless system, the EWUS during the EWUS monitoring occasion;determine that the EWUS indicates that the wireless device skip one ormore future EWUS monitoring occasions; and skip monitoring for the EWUSbased on the indicated skipped one or more future EWUS monitoringoccasions.

Example 17 comprises the subject matter of example 16, wherein thewireless device is further configured to: determine the EWUS indicatesthat the wireless device monitor a physical downlink control channel(PDCCH) instance in a next DRX cycle, wherein the PDCCH instance isassociated with the EWUS monitoring occasion; and monitor the PDCCHinstance in the next DRX cycle based on the EWUS.

Example 18 comprises the subject matter of example 17, wherein thewireless device is further configured to skip monitoring a PDCCHinstance associated with a next EWUS monitoring occasion.

Example 19 comprises the subject matter of example 16, wherein the EWUSindicates that the wireless device skip multiple EWUS monitoringoccasions and PDCCH monitoring instances associated with the multipleEWUS monitoring occasions, and wherein the wireless device is furtherconfigured to skip monitoring by skipping monitoring for the EWUS inmultiple DRX cycles based on the EWUS.

Example 20 comprises the subject matter of example 16, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 21 comprises the subject matter of example 20, wherein theencoded value is encoded in two bits of a downlink control message.

Example 22 comprises the subject matter of example 16, wherein the EWUSindicates that the wireless device skip multiple EWUS monitoringoccasions, and wherein the wireless device is further configured to skipmonitoring by skipping monitoring for the EWUS in multiple DRX cyclesbased on the EWUS.

Example 23 comprises the subject matter of example 22, wherein thewireless device is further configured to: determine the EWUS indicatesthat the wireless device monitor physical downlink control channel(PDCCH) instances in the multiple DRX cycles; and monitor the PDCCHinstances in the multiple DRX cycles based on the indication based onthe EWUS.

Example 24 comprises the subject matter of example 22, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 25 comprises the subject matter of example 16, wherein the EWUSindicates whether to skip monitoring a PDCCH instance associated with aEWUS monitoring occasion.

Example 26 comprises the subject matter of example 16, wherein the EWUSis transmitted in a downlink control message.

Example 27 comprises the subject matter of example 16, wherein the EWUSis associated with a predetermined default number of EWUS monitoringoccasions to skip.

According to Example 28, a method for power saying for a wirelessdevice, comprising: receiving, from the wireless system, configurationinformation indicating a discontinuous reception (DRX) cycle time, a DRXon time period, and an offset time; determining an enhanced wake-upsignal (EWUS) monitoring occasion for a DRX cycle based on the offsettime and the DRX on time period; monitoring, during a first DRX cycle,for an EWUS during the EWUS monitoring occasion associated with thefirst DRX cycle; receiving, from the wireless system, the EWUS duringthe EWUS monitoring occasion; determining that the EWUS indicates thatthe wireless device skip one or more future EWUS monitoring occasions;and skipping monitoring for the EWUS based on the indicated skipped oneor more future EWUS monitoring occasions,

Example 29 comprises the subject matter of example 28, wherein thewireless device is in an RRC idle mode.

Example 30 comprises the subject matter of example 28, wherein thewireless device is in an RRC inactive mode.

According to Example 31, a method for power saving, comprisingestablishing a radio resource control (RRC) connection with a wirelessdevice; transmitting, to the wireless device, configuration informationindicating a discontinuous reception (DRX) cycle time, a DRX on timeperiod, and an offset time; transmitting an enhanced wake-up signal(EWUS) monitoring occasion for a DRX cycle, the EWUS monitoring occasionbased on the offset time and the DRX on time period; determining thatthe wireless device can skip monitoring one or more future EWUSmonitoring occasions; transmitting, during a first DRX cycle, a EWUS forthe wireless device during the EWUS monitoring occasion associated withthe first DRX cycle, the EWUS indicating that the wireless device canskip the one or more future EWUS monitoring occasions; and skippingtransmitting the EWUS to the wireless device during the one or morefuture EWUS monitoring occasions.

Example 32 comprises the subject matter of Example 31, wherein the EWUSindicates that the wireless device monitor a physical downlink controlchannel (PDCCH) instance in a next DRX cycle, wherein the PDCCH instanceis associated with the EWUS monitoring occasion.

Example 33 comprises the subject matter of Example 31, and furthercomprising: determining to transmit data to the wireless device in twoor more physical downlink control channel (PDCCH) messages; anddetermining a number of PDCCH messages to transmit, and wherein the oneor more future EWUS monitoring occasions are determined based on thenumber of PDCCH messages to transmit.

Example 34 comprises the subject matter of Example 33, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 35 comprises the subject matter of Example 31, wherein skippingtransmitting the EWUS comprises skipping transmitting the EWUS in a nextEWUS monitoring occasion, and further comprising skipping transmitting aPDCCH message associated with the next EWUS monitoring occasion.

Example 36 comprises the subject matter of example 31, furthercomprising determining not to s a first number of physical downlinkcontrol channel (PDCCH) messages to the wireless device, wherein thefirst number is two or more, wherein the EWUS indicates the first numberof skipped EWUS transmissions to the wireless device, and whereinskipping transmitting the EWUS includes skipping transmitting a PDCCHmessage associated with the skipped EWUS transmission.

Example 37 comprises the subject matter of example 31, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions and PDCCH monitoring instances associated with the multipleEWUS monitoring occasions to skip.

Example 38 comprises the subject matter of Example 31, wherein the EWUSis transmitted in a downlink control message.

Example 39 comprises the subject matter of Example 31, wherein the EWUSindicates whether to skip monitoring a PDCCH instance associated with aEWUS monitoring occasion.

Example 40 comprises the subject matter of Example 31, wherein the EWUSis associated with a predetermined default number of EWUS monitoringoccasions to skip.

According to Example 41, a device comprising: an antenna; a radiooperably coupled to the antenna; and a processor operably coupled to theradio; wherein the device is configured to: establish a radio resourcecontrol (RRC) connection with a wireless device; transmit, to thewireless device, configuration information indicating a discontinuousreception (DRX) cycle time, a DRX on time period, and an offset time;transmit an enhanced wake-up signal (EWUS) monitoring occasion for a DRXcycle, the EWUS monitoring occasion based on the offset time and the DRXon time period; determine that the wireless device can skip monitoringone or more future EWUS monitoring occasions; transmit, during a firstDRX cycle, a EWUS for the wireless device during the EWUS monitoringoccasion associated with the first DRX cycle, the EWUS indicating thatthe wireless device can skip the one or more future EWUS monitoringoccasions; and skip transmitting the EWUS to the wireless device duringthe one or more future EWUS monitoring occasions.

Example 42 comprises the subject matter of Example 41, wherein the EWUSindicates that the wireless device monitor a physical downlink controlchannel (PDCCH) instance in a next DRX cycle, wherein the PDCCH instanceis associated with the EWUS monitoring occasion.

Example 43 comprises the subject matter of Example 41, wherein thedevice is further configured to: determine to transmit data to thewireless device in two or more physical downlink control channel (PDCCH)messages; and determine a number of PDCCH messages to transmit, andwherein the one or more future EWUS monitoring occasions are determinedbased on the number of PDCCH messages to transmit.

Example 44 comprises the subject matter of Example 43, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 45 comprises the subject matter of Example 41, wherein thedevice is configured to skip transmitting the EWUS by skippingtransmitting the EWUS in a next EWUS monitoring occasion; and whereinthe device is further configured to skip transmitting a PDCCH messageassociated with the next EWUS monitoring occasion.

Example 46 comprises the subject matter of Example 41, wherein thedevice is further configured to determine not to transmit a first numberof physical downlink control channel (PDCCH) messages to the wirelessdevice, wherein the first number is two or more, wherein the EWUSindicates the first number of skipped EWUS transmissions to the wirelessdevice, and wherein skipping transmitting the EWUS includes skippingtransmitting a PDCCH message associated with the skipped EWUStransmission.

Example 47 comprises the subject matter of Example 41, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions and PDCCH monitoring instances associated with the multipleEWUS monitoring occasions to skip.

Example 48 comprises the subject matter of Example 41, wherein the EWUSis transmitted in a downlink control message.

Example 49 comprises the subject matter of Example 41, wherein the EWUSindicates whether to skip monitoring a PDCCH instance associated with aEWUS monitoring occasion.

Example 50 comprises the subject matter of Example 41, wherein the EWUSis associated with a predetermined default number of EWUS monitoringoccasions to skip.

According to Example 51, a non-transitory computer readable mediumcomprising computer readable code executable by a processor to:establish a radio resource control (RRC) connection with a wirelessdevice; transmit, to the wireless device, configuration informationindicating a discontinuous reception (DRX) cycle time, a DRX on timeperiod, and an offset time; transmit an enhanced wake-up signal (EWUS)monitoring occasion for a DRX cycle, the EWUS monitoring occasion basedon the offset time and the DRX on time period; determine that thewireless device can skip monitoring one or more future EWUS monitoringoccasions; transmit, during a first DRX cycle, an EWUS for the wirelessdevice during the EWUS monitoring occasion associated with the first DRXcycle, the EWUS indicating that the wireless device can skip the one ormore future EWUS monitoring occasions; and skip transmitting the EWUS tothe wireless device during the one or more future EWUS monitoringoccasions.

Example 52 comprises the subject matter of Example 51, wherein the EWUSindicates that the wireless device monitor a physical downlink controlchannel (PDCCH) instance in a next DRX cycle, wherein the PDCCH instanceis associated with the EWUS monitoring occasion. 101741 Example 53comprises the subject matter of Example 51, wherein the device isfurther configured to: determine to transmit data to the wireless devicein two or more physical downlink control channel (PDCCH) messages; anddetermine a number of PDCCH messages to transmit, and wherein the one ormore future EWUS monitoring occasions are determined based on the numberof PDCCH messages to transmit.

Example 54 comprises the subject matter of Example 53, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.

Example 55 comprises the subject matter of Example 51, wherein thedevice is configured to skip transmitting the EWUS by skippingtransmitting the EWUS in a next EWUS monitoring occasion; and whereinthe device is further configured to skip transmitting a PDCCH messageassociated with the next EWUS monitoring occasion.

Example 56 comprises the subject matter of Example 51, wherein thedevice is further configured to determine not to transmit a first numberof physical downlink control channel (PDCCH) messages to the wirelessdevice, wherein the first number is two or snore, wherein the EWUSindicates the first number of skipped EWUS transmissions to the wirelessdevice, and wherein skipping transmitting the EWUS includes skippingtransmitting a PDCCH message associated with the skipped EWUStransmission.

Example 57 comprises the subject matter of Example 51, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions and PDCCH monitoring instances associated with the multipleEWUS monitoring occasions to skip.

Example 58 comprises the subject matter of Example 51, wherein the EWUSis transmitted in a downlink control message.

Example 59 comprises the subject matter of Example 51, wherein the EWUSindicates whether to skip monitoring a PDCCH instance associated with aEWUS monitoring occasion.

Example 60 comprises the subject matter of Example 51, wherein the EWUSis associated with a predetermined default number of EWUS monitoringoccasions to skip.

According to Example 61, a method that includes any action orcombination of actions as substantially described herein in the DetailedDescription.

According to Example 62, a method as substantially described herein withreference to each or any combination of the Figures included herein orwith reference to each or any combination of paragraphs in the DetailedDescription.

According to Example 63, a wireless device configured to perform anyaction or combination of actions as substantially described herein inthe Detailed Description as included in the wireless device,

According to Example 64, a wireless station configured to perform anyaction or combination of actions as substantially described herein inthe Detailed Description as included in the wireless station.

According to Example 65, a non-volatile computer-readable medium thatstores instructions that, when executed, cause the performance of anyaction or combination of actions as substantially described herein inthe Detailed Description.

According to Example 66, an integrated circuit configured to perform anyaction or combination of actions as substantially described herein inthe Detailed Description.

Yet another exemplary aspect may include a method, comprising, by adevice, performing any or all parts of the preceding Examples.

A yet further exemplary aspect may include a non-transitorycomputer-accessible memory medium comprising program instructions which,when executed at a device, cause the device to implement any or allparts of any of the preceding Examples.

A still further exemplary aspect may include a computer programcomprising instructions for performing any or all parts of any of thepreceding Examples.

Yet another exemplary aspect may include an apparatus comprising meansfor performing any or all of the elements of any of the precedingExamples.

Still another exemplary aspect may include an apparatus comprising aprocessor configured to cause a device to perform any or all of theelements of any of the preceding Examples.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users, In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should is be clearly indicated tousers.

Aspects of the present disclosure may be realized in any of variousforms. For example, some aspects may be realized as acomputer-implemented method, a computer- readable memory medium, or acomputer system. Other aspects may be realized using one or morecustom-designed hardware devices such as ASICs. Still other aspects maybe realized using one or more programmable hardware elements such asFPGAs.

In some aspects, a non-transitory computer-readable memory medium may beconfigured so that it stores program instructions and/or data, where theprogram instructions, if executed by a computer system, cause thecomputer system to perform a method, e.g., any of a method aspectsdescribed herein, or, any combination of the method aspects describedherein, or, any subset of any of the method aspects described herein,or, any combination of such subsets.

In some aspects, a device (e.g., a UE 106, a BS 102, a network element600) may be configured to include a processor (or a set of processors)and a memory medium, where the memory medium stores programinstructions, where the processor is configured to read and execute theprogram instructions from the memory medium, where the programinstructions are executable to implement any of the various methodaspects described herein (or, any combination of the method aspectsdescribed herein, or, any subset of any of the method aspects describedherein, or, any combination of such subsets). The device may be realizedin any of various forms.

Although the aspects above have been described in considerable detail,numerous variations and modifications will become apparent to thoseskilled in the art once the above disclosure is fully appreciated. It isintended that the following claims be interpreted to embrace all suchvariations and modifications.

1. A method for power saving for a wireless device, comprising:establishing a radio resource control (RRC) connection with a wirelesssystem; entering an RRC connected mode based on the established RRCconnection; receiving, from the wireless system, configurationinformation indicating a discontinuous reception (DRX) cycle time, a DRXon time period, and an offset time; determining an enhanced wake-upsignal (EWUS) monitoring occasion for a DRX cycle based on the offsettime and the DRX on time period; monitoring, during a first DRX cycle,for an EWUS during the EWUS monitoring occasion associated with thefirst DRX cycle; receiving, from the wireless system, the EWUS duringthe EWUS monitoring occasion; determining that the EWUS indicates thatthe wireless device skip one or more future EWUS monitoring occasions;and skipping monitoring for the EWUS based on the indicated skipped oneor more future EWUS monitoring occasions.
 2. The method of claim 1,further comprising: determining the EWUS indicates that the wirelessdevice monitor a physical downlink control channel (PDCCH) instance in anext DRX cycle, wherein the PDCCH instance is associated with the EWUSmonitoring occasion; and monitoring the PDCCH instance in the next DRXcycle based on the EWUS.
 3. The method of claim 2, further comprisingskipping monitoring a PDCCH instance associated with a next EWUSmonitoring occasion.
 4. The method of claim 1, wherein the EWUSindicates that the wireless device skip multiple EWUS monitoringoccasions and PDCCH monitoring instances associated with the multipleEWUS monitoring occasions, and wherein skipping monitoring comprisesskipping monitoring for the EWUS in multiple DRX cycles based on theEWUS.
 5. The method of claim 4, wherein the EWUS includes an encodedvalue indicating a number of EWUS monitoring occasions to skip.
 6. Themethod of claim 5, wherein the encoded value is encoded in two bits of adownlink control message.
 7. The method of claim 1, wherein the EWUSindicates that the wireless device skip multiple EWUS monitoringoccasions, and wherein skipping monitoring comprises skipping monitoringfor the EWUS in multiple DRX cycles based on the EWUS.
 8. (canceled) 9.The method of claim 7, wherein the EWUS includes an encoded valueindicating a number of EWUS monitoring occasions to skip. 10-12.(canceled)
 13. A method for power saving for a wireless device,comprising: receiving, from the wireless system, configurationinformation indicating a discontinuous reception (DRX) cycle time, a DRXon time period, and an offset time; determining an enhanced wake-upsignal (EWUS) monitoring occasion for a DRX cycle based on the offsettime and the DRX on time period; monitoring, during a first DRX cycle,for an EWUS during the EWUS monitoring occasion associated with thefirst DRX cycle; receiving, from the wireless system, the EWUS duringthe EWUS monitoring occasion; determining that the EWUS indicates thatthe wireless device skip one or more future EWUS monitoring occasions;and skipping monitoring for the EWUS based on the indicated skipped oneor more future EWUS monitoring occasions.
 14. The method of claim 13,wherein the wireless device is in an RRC idle mode or an RRC inactivemode.
 15. (canceled)
 16. A wireless device comprising: an antenna; aradio operably coupled to the antenna; and a processor operably coupledto the radio; wherein the wireless device is configured to: establish aradio resource control (RRC) connection with a wireless system; enter anRRC connected mode based on the established RRC connection; receive,from the wireless system, configuration information indicating adiscontinuous reception (DRX) cycle time, a DRX on time period, and anoffset time; determine an enhanced wake-up signal (EWUS) monitoringoccasion for a DRX cycle based on the offset time and the DRX on timeperiod; monitor, during a first DRX cycle, for an EWUS during the EWUSmonitoring occasion associated with the first DRX cycle; receive, fromthe wireless system, the EWUS during the EWUS monitoring occasion;determine that the EWUS indicates that the wireless device skip one ormore future EWUS monitoring occasions; and skip monitoring for the EWUSbased on the indicated skipped one or more future EWUS monitoringoccasions.
 17. The wireless device of claim 16, wherein the wirelessdevice is further configured to: determine the EWUS indicates that thewireless device monitor a physical downlink control channel (PDCCH)instance in a next DRX cycle, wherein the PDCCH instance is associatedwith the EWUS monitoring occasion; and monitor the PDCCH instance in thenext DRX cycle based on the EWUS.
 18. The wireless device of claim 17,wherein the wireless device is further configured to skip monitoring aPDCCH instance associated with a next EWUS monitoring occasion.
 19. Thewireless device of claim 16, wherein the EWUS indicates that thewireless device skip multiple EWUS monitoring occasions and PDCCHmonitoring instances associated with the multiple EWUS monitoringoccasions, and wherein the wireless device is further configured to skipmonitoring by skipping monitoring for the EWUS in multiple DRX cyclesbased on the EWUS.
 20. The wireless device of claim 16, wherein the EWUSincludes an encoded value indicating a number of EWUS monitoringoccasions to skip.
 21. (canceled)
 22. The wireless device of claim 16,wherein the EWUS indicates that the wireless device skip multiple EWUSmonitoring occasions, and wherein the wireless device is furtherconfigured to skip monitoring by skipping monitoring for the EWUS inmultiple DRX cycles based on the EWUS.
 23. The wireless device of claim22, wherein the wireless device is further configured to: determine theEWUS indicates that the wireless device monitor physical downlinkcontrol channel (PDCCH) instances in the multiple DRX cycles; andmonitor the PDCCH instances in the multiple DRX cycles based on theindication based on the EWUS.
 24. The wireless device of claim 22,wherein the EWUS includes an encoded value indicating a number of EWUSmonitoring occasions to skip.
 25. The wireless device of claim 16,wherein the EWUS indicates whether to skip monitoring a PDCCH instanceassociated with a EWUS monitoring occasion.
 26. The wireless device ofclaim 16, wherein the EWUS is transmitted in a downlink control message.27-36. (canceled)